---
title: File and maintain appeals
summary: Load, edit, and save appeals, extensions, and oral-argument schedule records.
status: draft
owner: <owner>
last_reviewed: 2026-08-21
operation_id: OP-APP-004
trigger: User saves frmAppeal
---

# File and maintain appeals

This workflow loads the active appeal for a case, manages extension and oral-argument grids, and persists appeal changes while keeping claim context and security stable.

| Field | Value |
| --- | --- |
| **Operation ID** | OP-APP-004 |
| **Trigger** | User saves [frmAppeal](../../screens/frm-appeal.md) |
| **Libraries involved** | [SAIF.Application.Claim.Legal](../../libraries/saif-application-claim-legal/overview.md), [SAIF.Business.Claim.Legal](../../libraries/saif-business-claim-legal/overview.md), [SAIF.Application.Claim](../../libraries/saif-application-claim/overview.md) |
| **Screens** | [frmAppeal](../../screens/frm-appeal.md) |
| **Inputs** | Appeal, extension, and oral-argument grid edits |
| **Outputs** | Persisted `clsAppeal`, `clsAppealExtension`, and linked schedule records; refreshed appeal list |

## Steps

1. `clsAppealManager` runs [frmAppeal](../../screens/frm-appeal.md), loads the active appeal, and manages extension and oral-argument grids — owned by [SAIF.Application.Claim.Legal](../../libraries/saif-application-claim-legal/overview.md).
2. [SAIF.Business.Claim.Legal](../../libraries/saif-business-claim-legal/overview.md) persists `clsAppeal`, `clsAppealExtension`, and the schedule records linked to oral arguments ([APPEAL](../../libraries/saif-business-claim-legal/database-tables.md#appeal), [APPEAL_EXTENSION](../../libraries/saif-business-claim-legal/database-tables.md#appeal_extension)).
3. `SAIF.Application.Claim.Legal` runs pre-save and post-save processing, reloads the current case, and returns the screen to the refreshed appeal list.
   - Access to the screen remains subject to the default-restricted-access rule ([BR-APP-002](../business-rules.md#br-app-002-default-restricted-access-with-explicit-role-escalation)).
4. `ClaimAppManager` keeps claim context and claim-security state stable while the appeal workflow changes the legal-case view — owned by [SAIF.Application.Claim](../../libraries/saif-application-claim/overview.md).

## Process flow

The following diagram visualizes this workflow across components.

```mermaid
flowchart TD
	Start([User saves frmAppeal]) --> S1[clsAppealManager loads active appeal and grids]
	S1 --> S2[SAIF.Business.Claim.Legal persists appeal, extension, schedule records]
	S2 --> S3[Pre-save/post-save processing runs]
	S3 --> S4[Case reloaded; claim context held stable]
	S4 --> EndOk([Refreshed appeal list displayed])
```

## Failure and edge-case behavior

- View-only or no-access users: save actions are blocked by the default-restricted-access rule until an explicit update role is granted ([BR-APP-002](../business-rules.md#br-app-002-default-restricted-access-with-explicit-role-escalation)).

## Related documentation
- [Operations and processes](../operations-processes.md)
- [Business rules](../business-rules.md)
- [Data model](../data-model.md)

## Sources
- `SAIF.Application.Claim.Legal/LegalNet/clsAppealManager.vb`
- `SAIF.Application.Claim/ClaimAppManager.vb`